Requirement Definition Using Seam Approach (case Study of Academic Information System

Requirement elicitation is an important stage on a system development life cycle. Unclear requirement definition would impact the system quality generally. Some methods was introduced and implemented on requirement definition such as Joint Requirement Definition (JRD) or VORD which tempted to anticipate and fulfill all stakeholder expectations. SEAM, has been successfully used as an approach to define the enterprise architecture and can implement on some level of hierarchical view of the problem domain. The systemic and systematic approach of SEAM can switch the view of system as a whole system as well as a composite system. This method can define elements of system stakeholders, the services they need and the collaboration among them. This paper describes implementation of SEAM approach into requirement definition process of Academic Information System. The SEAM approach adoption divides into 5 stages from define segment view into define the business process, and result of adopted SEAM matrix. This paper does not emphasize how to breakdown the SEAM into software level, but stresses to find the required specification of the system. The results show that SEAM can use as an alternative approach to define the system requirements especially when the system involved many stakeholders.